Previous variant was finding Lua 2 times, re-pushed. New logic: if detected Lua does not work, try Lua 5.1 once more.

Just tried on virtual FreeBSD10 (Clang 3.3, Lua 5.1+Lua 5.2+Luabind 0.9.1 for Lua 5.1).

Current develop build fails (luabind uses 5.1, not 5.2 in includes). This branch detects that 5.2 is not suitable for luabind and compiles successfully with 5.1 version:

-- Found Lua52: /usr/local/lib/liblua-5.2.so;/usr/lib/libm.so
-- Looking for LuaJIT 5.2
-- Could NOT find LUAJIT (missing:  LUAJIT_LIBRARIES LUAJIT_INCLUDE_DIR)
-- Looking for Luabind...
-- Found Luabind: /usr/local/lib/libluabind.so
-- Found Luabind: /usr/local/lib/libluabind.so
-- Performing Test LUABIND_WORKS
-- Performing Test LUABIND_WORKS - Failed
Luabind does not work with /usr/local/lib/liblua-5.2.so, will try Lua 5.1.
-- Found Lua51: /usr/local/lib/liblua-5.2.so;/usr/lib/libm.so (found version "5.1.5")
-- Performing Test LUABIND51_WORKS
-- Performing Test LUABIND51_WORKS - Success
Luabind works with Lua 5.1 at /usr/local/lib/liblua-5.1.so

(seems to work, rebased to develop)
However, this test slows down compilation for a few seconds.

However, this test slows down compilation for a few seconds.

A couple of seconds are totally fine.

@alex85k Any updates here?

Oh, I missed the Appveyor tests failures (thought it works already) on Release build. Will try to check this evening.

Cool, looking forward!

It was always compiling test sources with Debug configuration.
Hope the magic line

SET (CMAKE_TRY_COMPILE_CONFIGURATION ${CMAKE_BUILD_TYPE})

will help :)

(re-pushed after fixing variable names)

Seems to work this time.

Great. I'll work on getting this merged today.

Thanks again, great work!